Resource StructureDefinition/FHIR Server from package ehelse.fhir.no.grunndata.test#2.3.3 (78 ms)
Resources that use this resource
Resources that this resource uses
Source
{
"resourceType" : "StructureDefinition",
"id" : "gd-Provenance",
"url" : "http://ehelse.no/fhir/StructureDefinition/gd-Provenance",
"version" : "2.3.1",
"name" : "GdProvenance",
"status" : "draft",
"date" : "2019-12-06",
"description" : "Provenance profile to be used on Grunndata. Person, Practitioner, Organization etc.\r\n\r\nThe GdProvenance profile describes the structure and coding of provenance information describing how FHIR resource instances (such as Person/RelatedPerson) change over time (activity) and what events (reason) caused these changes.",
"fhirVersion" : "4.0.0",
"kind" : "resource",
"abstract" : false,
"type" : "Provenance",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Provenance",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Provenance",
"path" : "Provenance",
"alias" : [
"Hendelse"
]
},
{
"id" : "Provenance.meta",
"path" : "Provenance.meta"
},
{
"id" : "Provenance.meta.versionId",
"path" : "Provenance.meta.versionId",
"definition" : "Grunndata: Provenance resources themself should probably not exist in more than one version.\r\n\r\nThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted."
},
{
"id" : "Provenance.id",
"path" : "Provenance.id",
"definition" : "Grunndata: Provenance resources for the Grunndata-services should identify their provenance by a counter identifier that identifies the sequence that the Provenance resources where registered on the Grunndata-service. \r\n\r\nThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"alias" : [
"Hendelseid"
],
"mustSupport" : true
},
{
"id" : "Provenance.target",
"path" : "Provenance.target",
"definition" : "Grunndata uses the target element to reference the UPDATED version of the resource instance, after the recorded activity described by the Provenance resource has taken place. This is one reason the references in the target element SHOULD always be version specific. There is one exception when the Provenance describes a Delete transaction (Delete activity), in that case the target contains the reference/identifier of the deleted version of the resource: http://hl7.org/fhir/provenance.html#removal\r\n\r\nThe Reference(s) that were generated or updated by the activity described in this resource. A provenance can point to more than one target if multiple resources were created/updated by the same activity.",
"example" : [
{
"label" : "version specific id",
"valueReference" : {
"reference" : "http://example.org/fhir/Observation/1x2/_history/2"
}
}
],
"mustSupport" : true
},
{
"id" : "Provenance.target.extension",
"path" : "Provenance.target.extension",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "url"
}
],
"rules" : "open"
}
},
{
"id" : "Provenance.target.extension:targetElement",
"path" : "Provenance.target.extension",
"sliceName" : "targetElement",
"definition" : "Grunndata uses this element(s) to reference what element in the target resourc is changed by this event.\r\n\r\nIn some cases when you provide a reference to another resource instance you also want to specificly express a reference to specific elements of the target resource. Can contain the reference to the element and the change in value.",
"alias" : [
"entitet"
],
"type" : [
{
"code" : "Extension",
"profile" : [
"http://hl7.no/fhir/StructureDefinition/reference-targetElement"
]
}
],
"mapping" : [
{
"identity" : "freg",
"map" : "entitet"
}
]
},
{
"id" : "Provenance.target.reference",
"path" : "Provenance.target.reference",
"example" : [
{
"label" : "version specific id",
"valueString" : "http://example.org/fhir/Patient/1x2/_history/2"
}
],
"mustSupport" : true
},
{
"id" : "Provenance.occurred[x]",
"path" : "Provenance.occurred[x]",
"definition" : "Grunndata: When the activity leading to the change occurred in another system (FREG ex.) This would be the registered dates from that system.\r\n\r\nThe period during which the activity occurred.",
"alias" : [
"ajourholdstidspunkt"
],
"mustSupport" : true,
"mapping" : [
{
"identity" : "freg",
"map" : "ajourholdstidspunkt"
}
]
},
{
"id" : "Provenance.recorded",
"path" : "Provenance.recorded",
"definition" : "Grunndata: The time the change was recorded by the Grunndata system (e.g. not when the change happened in the source system)\r\n\r\nThe instant of time at which the activity was recorded.",
"mustSupport" : true
},
{
"id" : "Provenance.policy",
"path" : "Provenance.policy",
"definition" : "Grunndata don't use this element.\r\n\r\nPolicy or plan the activity was defined by. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc.",
"mustSupport" : false
},
{
"id" : "Provenance.location",
"path" : "Provenance.location",
"definition" : "Grunndata don't use this element.\r\n\r\nWhere the activity occurred, if relevant.",
"mustSupport" : false
},
{
"id" : "Provenance.reason",
"path" : "Provenance.reason",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "coding.system"
}
],
"rules" : "open"
},
"definition" : "Grunndata uses the reason code to communicate the original change event type from the data source, usually FREG event types.\r\n\r\nThe reason that the activity was taking place.",
"mustSupport" : true
},
{
"id" : "Provenance.reason:fregEventtype",
"path" : "Provenance.reason",
"sliceName" : "fregEventtype",
"short" : "Event type from FREG",
"definition" : "The event type from FREG that thescribes the change to the Master Person Index in some detail.",
"alias" : [
"hendelsestype"
],
"max" : "1",
"mustSupport" : true,
"binding" : {
"strength" : "required",
"valueSet" : "http://ehelse.no/fhir/ValueSet/gd-provenance-freg-eventtype"
},
"mapping" : [
{
"identity" : "freg",
"map" : "hendelsestype"
}
]
},
{
"id" : "Provenance.reason:fregEventtype.coding",
"path" : "Provenance.reason.coding",
"max" : "1"
},
{
"id" : "Provenance.reason:fregEventtype.coding.system",
"path" : "Provenance.reason.coding.system",
"short" : "Event type codesystem from freg",
"definition" : "Event type codesystem from freg",
"min" : 1,
"fixedUri" : "http://ehelse.no/fhir/CodeSystem/gd-provenance-freg-eventtype"
},
{
"id" : "Provenance.reason:fregEventtype.coding.code",
"path" : "Provenance.reason.coding.code",
"min" : 1
},
{
"id" : "Provenance.activity",
"path" : "Provenance.activity",
"definition" : "Grunndata uses this element to document what kind of transaction changed the content of the resource. Only codes identifying Data operation types will be used: http://terminology.hl7.org/CodeSystem/v3-DataOperation\r\nThe subset is defined in http://ehelse.no/fhir/ValueSet/gd-provenance-activity-type\r\n\r\nAn activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.",
"alias" : [
"Data Operation"
],
"mustSupport" : true,
"binding" : {
"strength" : "extensible",
"valueSet" : "http://ehelse.no/fhir/ValueSet/gd-provenance-activity-type"
}
},
{
"id" : "Provenance.activity.coding.system",
"path" : "Provenance.activity.coding.system",
"definition" : "The subset of http://terminology.hl7.org/CodeSystem/v3-DataOperation defined in http://ehelse.no/fhir/ValueSet/gd-provenance-activity-type\r\n\r\nThe identification of the code system that defines the meaning of the symbol in the code.",
"min" : 1,
"fixedUri" : "http://terminology.hl7.org/CodeSystem/v3-DataOperation"
},
{
"id" : "Provenance.activity.coding.code",
"path" : "Provenance.activity.coding.code",
"min" : 1
},
{
"id" : "Provenance.agent",
"path" : "Provenance.agent",
"definition" : "Grunndata uses who.display value to describe the organization responsible for the change.\r\n\r\nAn actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place.",
"mustSupport" : true
},
{
"id" : "Provenance.agent.who.display",
"path" : "Provenance.agent.who.display",
"definition" : "Grunndata uses display value to describe the organization responsible for the change.\r\n\r\nPlain text narrative that identifies the resource in addition to the resource reference.",
"mustSupport" : true
},
{
"id" : "Provenance.entity",
"path" : "Provenance.entity",
"definition" : "Grunndata uses this element to identify the resources updated during the activity recorded by the Provenance resource. Should be version specific reference to resources that are updated. \r\nWhen the provenance records the first generation of a resource the entity element can be empty.\r\n\r\nAn entity used in this activity.",
"meaningWhenMissing" : "When the provenance records the first generation of a resource the entity element can be empty.",
"mustSupport" : true
},
{
"id" : "Provenance.entity.role",
"path" : "Provenance.entity.role",
"definition" : "Grunndata will use revision | quotation | source | removal. In most cases the entity will have the role of \"source\"\r\n\r\nHow the entity was used during the activity.",
"mustSupport" : true
},
{
"id" : "Provenance.entity.what",
"path" : "Provenance.entity.what",
"definition" : "Grunndata uses this element to identify the resources updated during the activity recorded by the Provenance resource. Should be version specific reference to resources that are updated.\r\n\r\nIdentity of the Entity used. May be a logical or physical uri and maybe absolute or relative.",
"mustSupport" : true
},
{
"id" : "Provenance.signature",
"path" : "Provenance.signature",
"comment" : "Grunndata don't use this element\r\n\r\nThe elements of the Signature Resource are for ease of access of these elements. For digital signatures (Xml DigSig, JWS), the non-repudiation proof comes from the Signature validation, which includes validation of the referenced objects (e.g. Resources) (a.k.a., Content) in the XML-Signature Detached form.",
"mustSupport" : false
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.